DOM renderer has now RGB support.

• without RGB
  

• with RGB
  

For those that dont see the difference in the pictures above here some more juicy truicy colors in the demo (font-size 3, cols 300, rows 100):

@Tyriar I am not sure about the canvas renderer whether it should be applied there at all, since it is a drop candidate. Any thoughts on this?

@jerch 😍

I think we should, the canvas renderer will likely take months to phase out (iff there are no issues with webgl).

canvas renderer has now preliminary RGB support. This is only hacked in for now and bypasses the cache, several conditions like inverting fg/bg does not work yet.
The canvas renderer needs more rework to integrate this nicely, things like flags, fg and bg span several levels of method descents and need to be harmonized with the CellData type.

Transition of the canvas renderer is done. RGB is for now always uncached, not sure if we ever want to cache those, the sheer amount of colors will invalidate the cache entries often. Might still be worth to try since most use cases will still only use a small set of colors.
A minor optimization might be to allow cached drawing of palette foreground on RGB background, but we should test first if the possible glyph border artefacts are bearable.

Technically this PR is ready for review, but I think we should get the pending PRs it relies on done first. In the meantime I gonna cleanup the new code and do more tests. The latter is cumbersome since we have no automated canvas tests at all. Maybe we get something rolling with node-canvas?

@jerch some conflicts are stacking up on this one.

@Tyriar This was expected, its due to #1878 and the reflow changes, both conflict in buffer changes.

Fixed a lot of merge conflicts